home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000259_misckit-reques…aska.et.byu.edu_Wed Sep 7 15:44:54 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
3KB
Return-Path: <misckit-request@alaska.et.byu.edu>
Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA00494; Wed, 7 Sep 94 15:44:44 -0600
Received: from YVAX2.BYU.EDU by alaska.et.byu.edu; Wed, 7 Sep 1994 10:40:57 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-9 #7277)
id <01HGTTBKEFHC934UXK@yvax.byu.edu>; Wed, 07 Sep 1994 10:40:39 -0600 (MDT)
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.3-9 #7277)
id <01HGTTBDA074934Y2Q@yvax.byu.edu>; Wed, 07 Sep 1994 10:40:26 -0600 (MDT)
Received: from hermes.gac.edu by alaska.et.byu.edu; Wed,
7 Sep 1994 10:36:12 -0600
Received: by hermes.gac.edu (8.6.9/GAC-1.0.R9309061) id LAA04943; Wed,
7 Sep 1994 11:36:22 -0500
Date: Wed, 07 Sep 1994 11:36:22 -0500
From: kane@gac.edu
Subject: Re: Work in progress...
To: misckit@alaska.et.byu.edu
Message-Id: <199409071636.LAA04943@hermes.gac.edu>
Content-Transfer-Encoding: 7BIT
Don Yacktman wrote:
> Several times in the past we have brought up the possibility
> of splitting the main library up into smaller libraries that
> can be included as needed so that it is unnecessary to
> include the whole big library. [...] But while I'm switching
> over, it would be very easy to divide things up a bit more
> if there is demand for it.
To sort of combine your two messages, I'd suggest leaving the
1.x.y versions the way things are. If more breakup is demanded,
fold that into the plan for 2.0.
I like the idea of breaking up along appkit/non-appkit lines.
Perhaps to generalize a bit more, breaking up along similar lines
to OpenStep, NEXTSTEP, and future Kits/Frameworks would be a
good idea (staying away from trademark'd names, of course).
I don't think shlibs/dynlibs < ~60KB are worthwhile, though, and
the number of libs should be kept reasonable (< 10). Hopefully,
any breakup would also be accompanied by a similar source breakup
into separate projects under the MiscKit project.
> One key problem that I forsee is that we will lose the
> HashTable class with the FoundationKit. Many MiscKit
> classes use HashTables in ways where a NSDictionary
> would be insufficient. So we will need a HashTable
> class which is equivalent to the NeXT HashTable object.
Could you elaborate on this? Looking at the OpenStep spec, it
looks to me like NSDictionary (with NSData,NSValue) will provide
more general functionality (probably using the new NSMapTable
stuff) than HashTable.
Christopher
kane@gac.edu